I agree with Tim; AFAIK the crosswind join is just joining at the (modified) crosswind leg of a standard overhead join (i.e. overhead the runway). Joining on the standard circuit crosswind position creates a high collision risk with departing and go-around traffic.

I don't know, is it? Most of my flying has been in the UK so I know the standard overhead join, which is a form of crosswind join (technically). I don't know how much a pure crosswind join is used.

is it worth adding crosswind join to the list?

Tim,

I can confirm that the latest Beta (31st July) has fixed the non-appearing popup menus for me. Thanks.

Simon

Cheers, I will look at that.

Tim,

Thanks for the reply. Another small bug (introduced on earlier version I think) is that the Setup 'gearwheel' icon in the setup menu is almost invisible on Android as it displays as white on pale grey - see image:



Simon

Thanks both for the feedback. We will attempt to address as many points as possible today and get another beta out, especially because of the popup problem.

Parallel runways where they have not been given appropriate L/R designators are a pain. I think we will just have to add some basic runway details to the menu underneath their designator, comprising of their surface and length.
The approach tools can become active at greater lengths than 20nm to your destination; please see the navigation options. I believe they can be shown up to 40-50 miles away. There are a couple of technical reasons that make it undesirable to make the tools available at any time.
I do like the idea of making Find VRP more easily accessible but the standard airfield menu is big and cumbersome enough already. I think the Direct To screen does actually provide some VRP-specific help here.
The blue marks indicate that precision information is known about the runway, and therefore the Pseudo-ILS feature is available.
I don't want to reverse the L/R and numbers on the runway perspective at the moment. At the moment it's the same code which draws that runway and all the other runways when you're sufficiently zoomed in to the map. It's done that way because that's how the designators look in real life.

I've been playing with this new feature in simulation mode for a bit now and think it's a really good addition and extremely well implemented as usual

A few comments:

1) The problem I mentioned above with menus not appearing in portrait mode also occurs on my Nexus 7.

2) The approach selection seems to become active at 20nm to destination - I would like to be able to select my approach earlier sometimes. Maybe this could be done by adding a 'Select Approach' option to the destination airfield context menu which is available at all times.

3) The 'Find Hold' when on the ground and 'Find VRP' when approaching are excellent additions. Again I would like to have the 'Find VRP' option added to the context menu for all airfields as sometimes one may receive a clearance something like "Clear transit overhead via November and Echo" and in unfamiliar airspace it would be nice to quickly locate the VRPs.

4) What are the two blue marks shown at the runway threshold in the airfield brief?

5) When the runway selected has L/R qualifiers the runway number shown in the airfield brief has a small number above a large 'L' or 'R' due to the simulated perspective and the runway number is hard to read. Perhaps swapping these so that the number is displayed nearest the threshold would solve this problem.

Simon

Selecting an approach with parallel runways where one is grass and one hard the popup menu doesn't differentiate.

Thanks, maybe try a larger device? We've been tinkering with the popups and haven't tested the new code on phones yet. I'll look in to it tomorrow.